fix: List page crashes and missing rows#40
Conversation
|
via Claude: ReviewBlockingEdit link breaks when The list page now uses the But When
The Non-blocking
|
|
Both issues confirmed and fixed: 1. Edit link (blocking): Added 2. Silent error swallowing (non-blocking): Changed the bare |
|
Looks good to me. @twoGiants are we OK with just logging the error for a developers into console, |
|
plz update ./docs/claude-progress.txt |
When fetchFileContent fails for a repo, return an error table item instead of null. This surfaces the failure to the user rather than silently hiding the repo from the list. Co-Authored-By: Claude <noreply@anthropic.com>
The list page now shows failed repos as error items instead of dropping them. Update the test to expect both items in the table and verify the failed repo appears by name. Co-Authored-By: Claude <noreply@anthropic.com>
| if (!funcYaml) return ''; | ||
|
|
||
| const { runtime } = parseNamespaceAndRuntime(funcYaml.content); | ||
| const { runtime } = parseFuncYaml(funcYaml.content); |
There was a problem hiding this comment.
This may also throw if there is syntax error in func.yaml, which results in infinite "Loading sources…".
Screencast.From.2026-06-19.13-44-41.mp4
However feel free to create separate bugreport/pr for this if you want.
|
This looks IMO good. Two nits:
|
| }), | ||
| ); | ||
| return items; | ||
| return results.filter((item): item is FunctionTableItem => item !== null); |
There was a problem hiding this comment.
Since we are returning nulls no more we might not need this filter.
There was a problem hiding this comment.
Issue addresed in Openshift repo's PR openshift#4
Replace '<UNKNOWN>' with empty strings so TextOrDash renders em dashes automatically. Add console.error for developer debugging. Remove the null filter since the catch block always returns an item now. Co-Authored-By: Claude <noreply@anthropic.com>
|
PR opened in Openshift repo openshift#4 |
Summary
loadFunctionTableItemsso a deleted GitHub repo no longer crashes the entire list page (repos that fail to load are silently skipped)func.yamlinstead of repo name as the correlation key, so cluster matching works when the two differparseNamespaceAndRuntimetoparseFuncYamland extract thenamefieldFixes SRVOCF-840
Test plan
namediffers from repo name. List page shows the func.yaml name and matches cluster status correctly